Displaying relevant user interface objects

ABSTRACT

Techniques for displaying relevant user interface objects when a device is placed into viewing position are disclosed. The device can update its display in response to user input. Display updates can be based on a logical arrangement of user interface information along a z-axis.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/033,551, filed Apr. 29, 2016, titled “DISPLAYING RELEVANT USERINTERFACE OBJECTS,” which is a national stage application under 35U.S.C. § 371 of International Patent Application No. PCT/US2013/067634,filed on Oct. 30, 2013, titled “DISPLAYING RELEVANT USER INTERFACEOBJECTS,” the contents of which are hereby incorporated by reference.

FIELD

The disclosed embodiments relate generally to user interfaces ofelectronic devices.

BACKGROUND

Advanced personal electronic devices can have small form factors.Exemplary personal electronic devices include but are not limited totablets and smart phones. Uses of such personal electronic devicesinvolve presentation and manipulation of user interface objects ondisplay screens that are designed to be small to complement the personalelectronic devices.

Exemplary user interface objects include digital images, video, text,icons, control elements such as buttons, and other graphics. As usedhere, the term icon refers to an image that is used to represent and tolaunch an application, consistent with its ordinary meaning in the art.In addition, a “widget,” which is used in the art to refer to asimplified view of an application, constitutes an icon, for purposes ofthis disclosure.

Existing user interfaces on reduced-size personal electronic devices canbe inefficient, as they may require multiple manipulations by a userbefore appropriate information is presented.

SUMMARY

Techniques for presenting user interface objects on a personalelectronics device are disclosed.

DESCRIPTION OF THE FIGURES

FIG. 1 illustrates an exemplary personal electronic device.

FIG. 2 illustrates an exemplary user interface.

FIG. 3 illustrates an exemplary user interface.

FIG. 4 illustrates an exemplary logical structure of a user interface.

FIG. 5 illustrates an exemplary user interface.

FIG. 6 illustrates an exemplary user interface.

FIG. 7 illustrates an exemplary computing system.

FIG. 8 illustrates an exemplary user interface.

FIG. 9 illustrates an exemplary user interface.

FIG. 10 illustrates an exemplary user interface.

FIG. 11 illustrates an exemplary user interface.

FIG. 12 illustrates an exemplary user interface.

FIG. 13 illustrates an exemplary user interface.

FIG. 14 illustrates an exemplary user interface.

FIG. 15 illustrates an exemplary user interface.

FIG. 16 illustrates an exemplary user interface.

FIG. 17 illustrates an exemplary user interface.

FIG. 18 illustrates an exemplary process for displaying user interfaceobjects.

DETAILED DESCRIPTION

In the following description of the disclosure and examples, referenceis made to the accompanying drawings in which it is shown by way ofillustration specific examples that can be practiced. It is to beunderstood that other examples can be practiced and structural changescan be made without departing from the scope of the disclosure.

FIG. 1 illustrates exemplary personal electronic device 100 (hereafterdevice 100). In the illustrated example, device 100 includes body 102.Device 100 can have touch-sensitive display screen (hereaftertouchscreen) 104.

Touchscreen 104 can include a display device, such as a liquid crystaldisplay (LCD), light-emitting diode (LED) display, organiclight-emitting diode (OLED) display, or the like, positioned partiallyor fully behind or in front of a touch sensor panel implemented usingany desired touch sensing technology, such as mutual-capacitance touchsensing, self-capacitance touch sensing, resistive touch sensing,projection scan touch sensing, or the like. Touchscreen 104 can allow auser to perform various functions by touching over hovering near thetouch sensor panel using one or more fingers or other object.

In some embodiments, device 100 can have one or more input mechanisms106 and 108. Input mechanisms 106 and 108, if included, can betouch-sensitive. Examples of touch-sensitive input mechanisms includetouch-sensitive buttons and touch-sensitive surfaces. Input mechanisms106 and 108, if included, can be physical. Examples of physical inputmechanisms include push buttons and rotatable mechanisms. Body 102,which can include a bezel, can have predetermined regions on the bezelthat act as input mechanisms. In some embodiments, device 100 can havean attachment mechanism. Such an attachment mechanism, if included, canpermit attachment of device 100 with clothing, jewelry, and otherwearable accessories, for example. For example, the attachment mechanismcan attach to hats, eyewear, earrings, necklaces, shirts, jackets,bracelets, watch straps, chains, trousers, belts, shoes, purses,backpacks, so forth.

In some embodiments, device 100 can have one or more pressure sensors(not shown) for detecting a force or pressure applied to touchscreen104. The force or pressure applied to touchscreen 104 can be used as aninput to device 100 to perform any desired operation, such as making aselection, entering or exiting a menu, causing the display of additionaloptions/actions, or the like. Different operations can be performedbased on the amount of force or pressure being applied to touchscreen104. The one or more pressure sensors can further be used to determine aposition that the force is being applied to touchscreen 104.

1. Displaying Relevant User Interface Objects

FIG. 2 illustrates exemplary device 100 worn by user 201, who is walkingtowards his vehicle 202. As user 201 moves device 100 into a viewingposition, device 100 displays a user interface screen 203 on touchscreen104, automatically. In some embodiments, the display elements oftouchscreen 104 are inactive until user 201 moves device 100 intoviewing position, meaning that the display elements of touchscreen 104are off or appear to be off In some embodiments, device 100 can rotatethe displayed contents of touchscreen 104 (e.g., between landscape andportrait modes) so that the displayed information is in a proper viewingorientation, regardless of whether device 100 is held upwards,downwards, or sideways by user 201.

User interface screen 203 includes user interface objects that device100 has determined to be the most relevant to the user this moment. Inparticular, screen 203 includes an icon 204 for unlocking vehicle 202,which is useful to user 201 as he approaches his vehicle. Screen 203also includes map icon 205 for accessing traffic information, which canbe useful to user 201 as he begins his trip. Screen 203 also includesicon 206 referencing an upcoming calendar event, which can be useful inproviding destination information. Sizes of displayed icons can berelative to their relevance. On screen 203, icon 204 is larger thanicons 205 and 206 because device 100 has concluded that the unlocking ofvehicle 202, provided via icon 204, is more relevant.

This user interface presentation is notable in that it prioritizes anddisplays a manageable subset of icons to user 201, even if many moreuser interface objects are available for display. Also, this userinterface is made available to user 201 without any user interfacenavigation input from the user, other than the raising of his arm (e.g.,without requiring user 201 to push a power-on or equivalent button). Inthis way, device 100 reduces the amount of user input required to invokean appropriate user interface action. This benefit is non-trivial,particularly because device 100 has a relatively small display screensize, as compared with smart phones and other electronic devices, whichcan impede a user's navigation of a larger user interface environment.

It is possible for the number of relevant user interface objects in agiven situation to exceed the number that can be reasonably displayedtogether on touchscreen 104, such as three as shown in FIG. 2. When thisis the case, device 100 can prioritize the most relevant icons—asdetermined by a computer-based relevance algorithm on device 100—forinitial display. In some embodiments, a user can bring the remainingrelevant icons onto the display using input mechanisms 106 or 108. Insome embodiments, a user can bring the remaining relevant icons onto thedisplay using touchscreen 104, such as by swiping touchscreen 104 with atouch object.

FIG. 3 illustrates the display of relevant icons over multiple userinterface screens. In the illustrated example, user interface screen 301was displayed on device 100 in response to an upward movement of thedevice. Screen 301 includes icons 302-304 representing relevantapplications, which can be icons 203-205 (FIG. 2) in some examples. Inresponse to a rotation of input mechanism 108 in direction 306, userinterface screen 311 becomes displayed on device 100. Screen 311 canshow a number of additional relevant icons 312-314 that are lessrelevant than those shown in screen 301. In a response to a furtherrotation of input mechanism 108 in the same direction 306, device 100can show user interface screen 321. Screen 321 can include another setof relevant icons 322-324 that are less relevant than those shown inscreen 311, which are in turn less relevant than those in screen 301.Input mechanism 108 can be a rotatable crown. In this way, a user cannavigate between multiple sets of relevant user interface objects (e.g.,icons) on device 100.

A user can launch an application that corresponds to a displayed icon bytouching (e.g., via a finger tap) the displayed icon. As used here, thelaunching of an application means that the application runs in theforeground of device 100 and is shown on-screen. FIG. 4 illustrates thisaspect. In the illustrated example, user interface screen 401 wasdisplayed on device 100 in response to a movement of the device intoviewing position. Screen 401 includes icon 402 representing a messagingapplication (e.g., supporting Short Message Service (SMS)) having fiveunread messages, as well as icons 403 and 404 representing otherapplications. In response to a tap on icon 402 from a touch object(e.g., finger 405), device 100 launches the corresponding messagingapplication and displays unread messages 412 on user interface screen411.

Under some usage conditions, a user may wish to navigate from themessaging application to another relevant application. For instance, theuser may wish to navigate to the music and map applications previouslyrepresented by icons 403 and 404 on screen 401. Device 100 can permitnavigation between these applications directly, without first returningto screen 401. In particular, a rotation of input mechanism 108 indirection 414 while screen 411 is displayed causes device 100 to displaythe music player represented by icon 403 on screen 421. Screen 421 caninclude music playback controls 423. A further rotation of inputmechanism 108 in direction 414 while screen 421 is displayed causesdevice 100 to display the map application represented by icon 404 onscreen 431. Screen 431 can include traffic information 432.

In some embodiments, screens 411, 421, and 431 include visual aids, suchas paging dots 415, 425, and 435, respectively, that identify therelative position of the currently displayed application along thesequence of applications accessible via input mechanism 108. Othervisual aids, such as scroll bars and screen-to-screen transitions, canalso be used to aid the user's identification of the currently displayeduser interface screen in relation to the larger set of available userinterface screens.

While the exemplary user interface screens depicted in FIGS. 2-4 areprimarily concerned with the efficient display of relevant userinterface objects, it should be noted that device 100 can include manymore user interface objects that should be accessible to a user, even iftheir relevance in the moment is not readily discernible. For example, auser may wish to play a game impulsively. Device 100 can permit usernavigation beyond relevant user interface objects to other userinterface objects. FIG. 5 illustrates this aspect.

In FIG. 5, user interface screen 501 is displayed on device 100 inresponse to movement of the device into viewing position. Screen 501includes icons 502-504 representing relevant applications, which can beicons 203-205 (FIG. 2) in some examples. In the illustrated example,device 100 has determined that only three user interface objects (i.e.,icons 502-504) are relevant at the moment. Thus, in response to arotation of input mechanism 108 in direction 505, device 100 displaysuser interface screen 511 having other user interface objects availablefor user selection on device 100. The icons shown on screen 511 can be auser's favorite icons, meaning that the icons of screen 511 are apredetermined subset of user interface objects available on device 100.In response to a further rotation of input mechanism 108 in direction505, device 100 displays user interface screen 521, which includes iconsthat represent all of the available applications on device 100. Becausethe size of the displayed icons on screen 521 may be too small for usernavigation, in response to a further rotation of input mechanism 108 indirection 505, device 100 displays screen 531, which has the effect ofzooming into a subset of the icons from screen 521 so that those iconsare displayed in larger size for user interaction.

The user interface navigation described with reference to FIG. 5 can belogically organized according to logical structure 600 depicted in FIG.6. In the illustrated example of FIG. 6, x-axis 601 and y-axis 602 forma plane co-planar with the touchscreen screen surface of device 100(FIG. 1), and z-axis 603 is perpendicular to the x/y-plane formed byaxes 601 and 602. Plane 604, in one example, corresponds to userinterface screen 501 (FIG. 5), while plane 605 corresponds to userinterface screen 511 (FIG. 5), and plane 607 corresponds to userinterface screens 521 and 531 (FIG. 5). More specifically, screen 521(FIG. 5) can correspond to a viewpoint of the entire content of plane607, while screen 531 (FIG. 5) can correspond to a zoomed in viewpoint(i.e., an enlarged subset) of the content of plane 607. In anotherexample, planes 604, 607, 608 can correspond to user interface screens301, 311, and 321 of FIG. 3, respectively. Movement of an inputmechanism can be used to select a particular plane of information (i.e.,screen of icons) for display on device 100. For example, rotation ofinput mechanism 108 can cause different screens of icons to be displayedon device 100 similar to the fashion depicted in FIG. 5, for example.

2. Determining Relevant User Interface Objects

Consistent with its plain meaning, the phrase “relevant icons” is usedhere to refer to user interface icons that bear upon or properly applyto the matter that is at hand. In the example of FIG. 2, an icon forunlocking a vehicle application is relevant as a user draws near hiscar, because the user is likely to want to drive the car. Device 100 candetermine relevance using computer instructions (e.g., algorithms) thataccount for different inputs, including sensor input, application data,and operating system data.

FIG. 7 depicts exemplary computing system 700 that, in some embodiments,form device 100. Computing 700 includes components for determining anddisplaying relevant user interface objects. In the illustrated example,computing system 700 includes an I/O section 704 that can be operativelycoupled (connected) with various sensors, such as GPS sensor 720,accelerometer 722, directional sensor 724, gyroscope 726, light sensor728, and/or a combination thereof. I/O section 704 also can be connectedwith communication unit 718, for receiving application and operatingsystem data, over Wi-Fi, Bluetooth™, near-field communication (“NFC”),cellular and other wireless communication techniques. In addition,computing system 700 can have bus 702 that connects I/O section 704together with one or more computer processors 706 and memory section708. Memory section 708 can contain computer-executable instructions(e.g., representing algorithms) and/or data for determining anddisplaying relevant user interface objects. One or more of thesecomponents can be part of an integrated chip or a so-calledsystem-on-a-chip. In addition, I/O section 704 can be connected to inputmechanism 714. I/O section 704 can be connected to one or more inputbuttons 716. I/O section 704 can be connected to display 710, which canhave touch-sensitive component 712 and, optionally, touch-pressuresensitive component 713.

The sensors and communication units of computing system 700 can provideinformation for identifying relevant user interface objects. Forexample, GPS sensor 720 can determine a user's location and movementwhile communication unit 718 can receive information about the locationand identity of a nearby vehicle (e.g., vehicle 202 in FIG. 2).Accelerometer 722, directional sensor 724, and gyroscope 726 can furtherdetect device movement. Optionally, the outputs of GPS sensor 720,accelerometer 722, directional sensor 724, and/or gyroscope 726 can beinterpreted by motion processor 730. Processors 706 andcomputer-executable instructions in memory section 708 can use some orall of this information to determine that the user is approaching hisvehicle. Processors 706 and instructions in memory 708 can alsodetermine, based on application data and/or operating system data(including meta-data) stored in memory 708, that an application forinteracting with the user's vehicle is installed. In this way, therelevance algorithms of device 100 can conclude that the vehicleinteraction application is relevant to the user in the moment. Inaddition, device 100 can also conclude, based on the same data, that amap application would also be relevant to the user.

Communication unit 718 can also receive other information that affectsthe relevance of user interface objects. For example, the communicationunit can detect nearby devices that are identical or similar, such asother wearable devices of the same design. The communication unit canalso detect non-identical units that are running the same operatingsystem as device 100, such as smart phones and tablets of the samebrand. The communication unit can also identify dissimilar devices thatsupport communication over a common protocol. These protocols caninclude wireless protocols such as Wi-Fi, Bluetooth™, NFC, and the like.These protocols can also be software-based service protocols, such asoperating environment service protocols (Apple™ AirPlay™ and AirDrop™),home automation service protocols (e.g., those offered by Phillips'Lighting and Nest™), authentication service protocols (e.g., airportclearance and metro fares), to point of sale service protocols (e.g., atgrocery checkouts), for example. The algorithms used by device 100 toidentify relevant user interface objects can account for these inputsprovided by the communication unit 718.

Furthermore, communication unit 718 can receive application andoperating system data that inform relevance. For example, a messagingapplication can receive an incoming message via SMS or Wi-Fi service,and thereby become relevant. As another example, the relevancealgorithms of device 100 can use calendar data and the cellular systemtime to determine that an event reminder is relevant. Furthermore, therelevance algorithms of device 100 can consider the content ofapplication and operating system data in determining relevance. Forexample, the algorithms can consider an incoming message that contains areference to a specific time (e.g., “let's meet at 3:00 p”) to beincreasingly relevant as that time (i.e., 3:00 pm) approaches.

In some embodiments, user interface objects can be relevant in groups.That is, application data (including meta-data) can specify thatwhenever user interface object A is relevant, that user interface objectB is also relevant. For example, a music application can be tied to avehicle interaction application in this way, because drivers typicallyenjoy music. A map application can also be tied to a vehicle interactionapplication in this way, because drivers typically desire traffic and/orrouting information.

In some embodiments, relevance algorithms used by device 100 can beadaptive, meaning that the outcome of the algorithms can change based onhistorical user behavior. For example, the algorithms can recognize auser's work commute based on the user's driving pattern during weekdaymornings. In this way, device 100 can prioritize specific trafficinformation for display in the morning. As another example, if a userrepeatedly launches one particular radio application over otheravailable radio applications during his commute, device 100 can identifythat radio application as being more relevant, and display its iconwhenever the user unlocks his car.

In some embodiments, computing system 700 can include biometric sensorssuch as health-related sensors such as photoplethysmograph (PPG)sensors, electrocardiography (ECG) sensors, and/or galvanic skinresponse (GSR) sensors. Device 100 can receive input from one or more ofthese sensors to provide health-related information. For example, device100 can use PPG sensor information to alert a user to abnormalrespiratory rate, blood pressure, and/or oxygen saturation. As anotherexample, device 100 can use an ECG sensor to alert a user to irregularheartbeats. As yet another example, device 100 can use a GSR sensor todetect a user's skin moisture indicative of sweating, and prioritize athermostat application for display on device 100. These sensors can alsobe used to facilitate biometric identification and authentication of auser.

The sensors of computing system 700 can detect when the system (e.g.,device 100) is placed into a viewing position. For example,accelerometer 724 and/or motion sensor 722 can detect when computingsystem 700 is raised, lowered, and shaken. These sensors can also detectwrist rotation forward and backward. In some embodiments, the raising ofcomputing device 700 is interpreted as a placement of the device intoviewing position. In some embodiment, the raising and rotation ofcomputing device 700 is interpreted as a placement of the device intoviewing position. In some embodiments, the time duration between theraising and lowering of computing device 700 is interpreted as aplacement of the device into viewing position.

Algorithms used by device 100 to identify relevant user interfaceobjects for display can use one or more of the above-described aspectsof the device (e.g., computing system 700). That is, the algorithms canconsider a combination of inputs in determining relevance, includinglocation, movement (including orientation, direction, tilt,acceleration, and velocity), ambient conditions (including light, time,temperature, user's health status), application data (including incomingcalls, incoming messages, upcoming calendar events).

For example, device 100 can determine that when it is moving at avelocity that exceeds a threshold (e.g., 10 mph, 20 mph, 25 mph, 30 mph,40 mph, 50 mph, 55 mph, 60 mph, 65 mph, so forth), the user of thedevice is commuting, and that icons corresponding to navigationalapplications have higher relevance. In this situation, device 100 canalso determine that icons representing in-vehicle entertainmentapplications are relevant, if an available in-vehicle device is incommunication with the communication unit of device 100. As anotherexample, device 100 can determine that when its biometric sensors andmotion sensors detect movement indicative of exercising, iconsrepresenting health-related applications have higher relevance. Asanother example, device 100 can determine that a calendar event that iscoming up in a particular amount of time (e.g., 15 minutes, 30 minutes,1 hour, 1 day, 1 week, so forth) is of higher relevance. Optionally,device 100 can factor in other variables, such as the distance betweenthe device's current location and the event's location, as well as thecurrent weather, in determining the relevance of an event. That is,device 100 may determine that a nearby event that is upcoming in 15minutes has less relevance than an event that is upcoming in an hour butis 30 miles away, for example.

3. Exemplary User Interactions

A user can interact with the user interface of device 100. Theseinteractions can include shortcuts for invoking applications features.This aspect is discussed with reference to FIGS. 8-9.

In the example of FIG. 8, device 100 had just received an incoming SMSmessage, and had provided haptic feedback to the user. In response tothe haptic feedback, the user raises device 100 into viewing position,thereby causing device 100 to display user interface screen 801. Screen801 includes icons 802-804 representing applications that it hasdetermined as being relevant to the user at the moment. Icon 802represents the unread SMS message. Icon 803 represents an upcomingcalendar event. Icon 804 represents available traffic information. Icon802 is displayed in large format because the SMS message, which wasrecently received, ranks highest in relevance.

Because messaging icon 802 has the highest relevance, when the userrotates input mechanism 108 in direction 805, device 100 launches thecorresponding messaging application and displays unread SMS message 812on user interface screen 811. In response to a further rotation of inputmechanism 108 in direction 805, device 100 displays calendar event 822in the calendar application represented by icon 803 on user interfacescreen 821. In response to a further rotation of input mechanism 108 indirection 805, device 100 displays traffic information provided by themap application (corresponding to icon 804) on user interface screen831.

From screen 811, a user may tap on SMS message 812 to invoke userinterface screen 901, shown in FIG. 9. Turning to FIG. 9, screen 901includes icon 902 for responding to SMS message 812. Screen 901 alsoincludes icon 903 for creating an alarm at 3 o'clock in the afternoon assuggested by SMS message 812. Similarly, when screen 821 (FIG. 8) isdisplayed, the user may tap on calendar event 822 to invoke userinterface screen 911, shown in FIG. 9. Screen 911 includes icon 912 formessaging an event attendee (e.g., Larry). Screen 911 also includes icon913 for obtaining navigation to the event location. Finally, when screen831 (FIG. 8) is displayed, a user may tap on map 832 to invoke userinterface screen 921, shown in FIG. 9. Screen 921 includes icon 922 forsetting a navigation waypoint and icon 923 for obtaining turn-by-turnnavigation instructions.

In some embodiments, device 100 can distinguish between short taps andlong taps on touch-screen 104 (FIG. 1), and invoke screen 901 only aftera long-tap on screen 811 (FIG. 8), for example. For purposes of thisdisclosure, a short tap refers to a brief touch on touchscreen 104(FIG. 1) followed by a release of the touch. A long tap refers to alonger touch on touchscreen 104 (FIG. 1) before touch release. Device100 can consider touches exceeding a predetermined duration to be longtaps (and touches of shorter duration to be short taps). In someembodiments, device 100 can distinguish between the level of pressure ontouchscreen 104. That is, device 100 can detect the intensity of a touchobject (e.g., a user's finger) on touchscreen 104. Thus, device 100 caninvoke screen 901 only after a user taps on screen 811 (FIG. 8.) withsufficient pressure.

In some embodiments, device 100 can distinguish between brief glancesand longer stares at touchscreen 104 (FIG. 1). A brief glance can becharacterized by having a short duration between the raising of thedevice into viewing position and the subsequent lowering of the device.A longer stare can be characterized by a period of relative steadinessof the device in the viewing position. Device 100 can respond to briefglances and longer stares differently. This aspect is illustrated byFIG. 10. In the example of FIG. 10, user interface screen 1001 wasdisplayed in response to a user's movement of device 100 into viewingposition. However, instead of displaying multiple relevant userinterface objects, user interface screen 1001 emphasizes the display ofan unread SMS message 1002 from a contact, because message 1002 hadarrived immediately before device 100 was raised into viewing position.If the user maintains device 100 in viewing position exceeding apredetermined time duration, device 100 replaces screen 1001 with userinterface screen 1011, which shows multiple icons representing relevantuser interface objects available on device 100. From screen 1011, theuser can tap on icon 1012 using finger 1013 to return to SMS message1002. In this way, device 100 permits a user to briefly glance at anincoming message.

4. Exemplary User Interfaces

FIGS. 11-16 illustrate exemplary user interfaces that device 100 candisplay, based on relevance, over the course of a day. In FIG. 11,device 100 determines that the user has recently awakened, and displaysan appropriate greeting 1102 stating “good morning”. Device 100 can makethis determination based on the time of day, the user's interaction withan alarm clock application (e.g., user may have just turned off analarm), and/or movement of the device that indicate the user is walkingafter a sedentary period, for example. Device 100 can rank greeting 1102as the most relevant icon to be displayed to a user as he wakes up.Because of its high relevance, greeting 1102 is emphasized on userinterface screen 1101, meaning that greeting 1102 can be largest icondisplayed, or the only icon displayed. Note, however, that when greeting1102 is the only icon displayed, other non-icon user interface elements(such as the current time) can still be displayed on-screen.

User interface screen 1111 depicts another exemplary user interface thatdevice 100 can display as its user wakes up. Screen 1111 includes icon1112 indicating the current time. Icon 1123 can have circumferentialoutline 1113 indicating the time remaining in snooze. Optionally, icon1112 can have a background that indicates the current weather, forexample, with blue representing temperate weather and gray representinginclement weather. Screen 1112 can also include icon 1115 indicatingunread messages that the user should attend to.

FIG. 12 illustrates user interface screen 1201, which can showadditional relevant user interface objects after a user wakes up. Screen1201 includes relevant icons 1202-1204. Icon 1202 can correspond to ahealth application and indicate sleep information, such as the durationof sleep by the user. Icon 1203 can correspond to calendar information,such as the remaining time before a next calendar event. Icon 1204 cancorrespond to additional calendar information, such as all-day events.

User interface screen 1211 depicts additional relevant user interfaceobjects that device 100 can display after a user wakes up. Screen 1211includes relevant icons 1212 and 1213. Icon 1212 can correspond to aweather application indicating the weather at the device's presentlocation. Optionally, icon 1212 can indicate the weather at a locationthat the user historically travels to in the morning, such as theweather at the user's work location. In addition, icon 1213 can indicatethat the user should begin his morning commute to work in 45 minutes.Device 100 can make this determination based on the first event intoday's calendar, the user's usual travel destination on weekdaymornings, and the estimated time of travel to that destination based ondistance and traffic information, for example.

User interface screen 1221 depicts additional relevant user interfaceobjects that device 100 can display later in the morning. Exemplary userinterface screen 1121 includes relevant icons 1222-1224. Icon 1222,which indicates weather condition, can display the same information thatwas displayed earlier by icon 1212. However, while icon 1212 was themost relevant icon on screen 1211, its relevance in screen 1221 issuperseded by traffic icon 1223. Traffic icon 1223 indicates a trafficalert and is displayed as the largest icon because device 100 hasdetermined that information about an accident along the user's typicalmorning commute is highly relevant at the moment. Screen 1221 alsoincludes icon 1224 indicating that the user should begin his commute towork in 10 minutes, rather than the 45 minute indication given earlierby icon 1213, in view of traffic information (caused by the accident)received by device 100.

Turning to FIG. 13, screen 1301 depicts icon 1302 for unlocking theuser's vehicle as he approaches his vehicle. Device 100 can display icon1302 based on decreasing distance between device 100 and his nearbyvehicle. Optionally, screen 1301 can include additional relevant icons,such as those discussed with respect to FIG. 1. While the user is in hiscar, device 100 can display user interface screen 1311 if it is raisedinto viewing position. Screen 1311 includes information about theestimate time to arrival (“ETA”) to work (i.e., icon 1312), the time tohis next calendared meeting (i.e., icon 1313), and the music player(i.e., as represented by icon 1314), which are relevant to the user ashe is en route to work. Device 100 can determine that the user isdriving based on GPS movement and/or by communication with an in-cartelematics system (e.g., through Bluetooth™ or a cable connection).Device 100 can determine that the user is driving to his work based onhistorical information about the user's commute pattern. As the usernears his workplace, the estimated time to arrival may become lessrelevant, causing the information to be displayed with less emphasis.For example, in user interface screen 1321, music icon 1322 is displayedin larger format than ETA icon 1224. Icon 1323 can continue to displaythe time to the next calendared meeting as the information continues tobe highly relevant. Device 100 can mark the reminder as highly relevantif the meeting is off-site (i.e., physically far from the user's worklocation), based on GPS sensor and calendar information.

Turning to FIG. 14, later in the day, the user of device 100 can visit astore such as a coffee shop. On screen 1401, device 100 can display anelectronic-payment icon 1412 that permits the user to authorize apurchase at the coffee shop. Device 100 can determine its proximity tothe coffee shop based on GPS information and application data providedby a map application or a third-party application, such as a Starbucks™application. Device 100 can also determine its proximity to the coffeeshop based on wireless communication with the store's point-of-salesystem, such as through near-field communication with a payment reader.In addition, on screen 1401, device 100 can display icon 1403 indicatingthe proximity of a contact (e.g., a friend) at the coffee shop. Onscreen 1411, device 100 can display icon 1412 indicating a new incomingmessage, icon 1413 counting down to an upcoming meeting, and icon 1414suggesting that the user should take the stairs to the meeting foradditional exercise. Device 100 can remind a user if he is late to ameeting. For example, on screen 1421, device 100 can display icon 1422alerting the user that the user is eight minutes late to a calendaredmeeting, and icons 1423 and 1424 alerting the user to new incomingmessages, some of which may have been triggered by his absence at themeeting.

Turning to FIG. 15, device 100 can display information relevant as theworkday draws to a close. On user interface screen 1501, device 100 candisplay the user's ETA to home (i.e., icon 1502) and his spouse's ETA tohome (i.e., icon 1503). On user interface screen 1511, device 100 cancontinue to display the user's ETA to home (i.e., icon 1512), a musicapplication to changing the music in his vehicle (i.e., icon 1513), anda stress level indicator (i.e., icon 1514). Device 100 can calculate theuser's stress level based on sensor input including, for example, PPG,ECG, and GSR sensor readings. As the user arrives home and looks atdevice 100, device 100 can display icon 1522 for unlocking awireless-enabled front-door door lock. Device 100 can also display icon1524 for controlling in-home electronics, such as lighting and furnacesettings, through Wi-Fi enabled lighting and HVAC controllers. Device100 can also display icon 1523 indicating a dinner event.

Turning to FIG. 16, device 100 can display information relevant as theday ends. On user interface screen 1601, device 100 can display icon1602 suggesting that the user should sleep soon, based on the user'susual sleep time and the next morning's calendared activities, forexample. Device 100 can also display icon 1604 for controllingtelevisions, based on the user's habit of watching television at night.Device 100 can also display icon 1603 for lighting control, also basedon the user's usual end-of-day routine. As the user's usual bed timecontinues to draw near, device 100 can display a summary of the user'sphysical activities for the day (i.e., icon 1612 indicating the user met75% of their daily goal), and an alarm clock icon 1613 for setting analarm for the next morning. Device 100 can also reduce the amount ofuser interface objects displayed at the end of the day. For example, asshown on screen 1621, device 100 can display a single icon 1622suggesting sleep. In addition, icon 1622 can be displayed using lightwavelengths that are less likely to interfere with a user's sleeppattern. In this way, device 100 can avoid keeping its user awake and/orawaking its sleeping user.

Optionally, device 100 can be configured to display a clock facepersistently. This aspect is described with respect to FIG. 17. In theillustrated example, device 100 displays user interface screen 1702 inresponse to the raising of the device into viewing position. On screen1702, clock 1702 is displayed together with relevant icon 1703. Asdevice 100 identifies additional relevant user interface objects, theycan be displayed in the foreground of touchscreen 104 (FIG. 1) about thecircumference of clock 1702, as demonstrated by additional relevanticons 1712 and 1713 on screens 1711 and 1721. In this way, a user canconfigure device 100 so as to emphasize its time-keeping function.

FIG. 18 depicts exemplary process 1800 that can be performed by device100 to display relevant user interface objects. At block 1810, device100 obtains input from a movement sensor indicating movement of thedevice into a viewing position. In some embodiments, the movement can bean upward movement. At block 1820, device 100 obtains additional sensordata. Such sensor data can include GPS location information, lightinginformation, movement information, and/or accelerometer information. Atblock 1830, device 100 obtains application or operating system data.Such data can be obtained through a communication channel such as Wi-Fi,Bluetooth™, or NFC. At block 1840, device 100 identifies, based on thesensor data and application/OS data, user interface objects that arerelevant for display to the user. Device 100 can also rank the relevantuser interface objects. At block 1850, the most relevant user interfaceobjects are displayed to the user. At block 1860, device 100 receives ainput representing movement of an input mechanism. In response, at block1870, device 100 displays icons representing the user's favoriteapplications available on the device. At block 1880, device 100 receivesan additional input representing movement of an input mechanism. Inresponse, at block 1890, device 100 displays icons representing all ofthe available applications on the device.

Turning back to FIG. 7, memory section 708 of computing system 700 canbe a non-transitory computer readable storage medium, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 706, for example, can cause the computer processorsto perform the user interface techniques described above, includingprocess 1800 (FIG. 18). The computer-executable instructions can also bestored and/or transported within any non-transitory computer readablestorage medium for use by or in connection with an instruction executionsystem, apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer readable storage medium” can be any medium thatcan contain or store computer-executable instructions for use by or inconnection with the instruction execution system, apparatus, or device.The non-transitory computer readable storage medium can include, but isnot limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as RAM, ROM, EPROM, flashmemory, and solid-state memory. Computing system 700 is not limited tothe components and configuration of FIG. 7, but can include other oradditional components in multiple configurations.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. An electronic device comprising: a display; amovement sensor configured to detect movement of the electronic device,a rotatable input mechanism configured to rotate with respect to ahousing of the electronic device; one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:detecting an input from the movement sensor based on a movement of theelectronic device; in response to detecting the input from the movementsensor, displaying, on the display, a first plurality of user interfaceobjects based on a relevance algorithm, wherein the first plurality ofuser interface objects is selected from a larger plurality of userinterface objects available for display, and wherein the first pluralityof user interface objects includes a first user interface objectassociated with a first application and having a first displayed sizecorresponding to a relevance of the first user interface objectdetermined based on the relevance algorithm; while displaying the firstplurality of user interface objects, receiving a user input, the userinput representing rotation of the rotatable input mechanism withrespect to the housing of the electronic device; in response toreceiving the user input, displaying, on the display, a second pluralityof user interface objects based on the relevance algorithm, wherein thesecond plurality of user interface objects is selected from the largerplurality of user interface objects available for display, and whereinthe second plurality of user interface objects includes a second userinterface object associated with a second application that is differentthan the first application and having a second displayed sizecorresponding to a relevance of the second user interface objectdetermined based on the relevance algorithm and different from the firstdisplayed size of the first user interface object; detecting updatedinput for use by the relevance algorithm; and after detecting theupdated input for use by the relevance algorithm, displaying the seconduser interface object based on the updated input for use by therelevance algorithm, including: in accordance with a determination thatthe relevance of a third user interface object determined based on therelevance algorithm is greater than the relevance of the second userinterface object, displaying the second user interface object having athird displayed size that is smaller than the second displayed size. 2.The device of claim 1, wherein the first user interface object includesdata corresponding to the first application associated with the firstuser interface object and the second user interface object includes datacorresponding to the second application associated with the second userinterface object.
 3. The device of claim 1, wherein the first userinterface object includes an affordance that causes an action associatedwith the first application to be taken when selected.
 4. The device ofclaim 1, wherein the second user interface object includes an affordancethat causes an action associated with the second application to be takenwhen selected.
 5. The device of claim 2, wherein the data correspondingto the first application associated with the first user interface objectcomprises a notification.
 6. The device of claim 2, wherein the datacorresponding to the second application associated with the second userinterface object comprises a notification.
 7. The device of claim 1,wherein the relevance algorithm uses as input at least one of a locationof the electronic device, a location of an external device, a currenttime, an upcoming calendar event, map information, or user healthinformation represented by input received from a biometric sensor. 8.The device of claim 1, the one or more programs further includinginstructions for: displaying a third user interface object and a fourthuser interface object, wherein the second user interface object, thethird user interface object, and the fourth user interface object areselected using the relevance algorithm, and wherein: the second userinterface object includes data associated with the second application,the third user interface object includes a notification associated witha third application, and the fourth user interface object includes anindication of an action associated with a fourth application.
 9. Thedevice of claim 1, wherein displaying the second plurality of userinterface objects on the display based on the relevance algorithmcomprises replacing the first plurality of user interface objects withthe second plurality of user interface objects on the display.
 10. Thedevice of claim 1, wherein the relevance algorithm increases a relevanceof the second user interface object from the larger plurality of userinterface objects available for display when a distance between thedevice and a location of an external device associated with theelectronic device decreases.
 11. The device of claim 1, wherein thefirst plurality of user interface objects further includes a third userinterface object, wherein the third user interface object overlaps thefirst user interface object on the display.
 12. A method, comprising: atan electronic device with a display, a movement sensor configured todetect movement of the electronic device, and a rotatable inputmechanism configured to rotate relative to a housing of the electronicdevice: detecting an input from the movement sensor based on a movementof the electronic device; in response to detecting the input from themovement sensor, displaying, on the display, a first plurality of userinterface objects based on a relevance algorithm, wherein the firstplurality of user interface objects is selected from a larger pluralityof user interface objects available for display, and wherein the firstplurality of user interface objects includes a first user interfaceobject associated with a first application and having a first displayedsize corresponding to a relevance of the first user interface objectdetermined based on the relevance algorithm; while displaying the firstplurality of user interface objects, receiving a user input, the userinput representing rotation of the rotatable input mechanism thatrotates with respect to a housing of the electronic device; in responseto receiving the user input, displaying, on the display, a secondplurality of user interface objects based on the relevance algorithm,wherein the second plurality of user interface objects is selected fromthe larger plurality of user interface objects available for display,and wherein the second plurality of user interface objects includes asecond user interface object associated with a second application thatis different than the first application and having a second displayedsize corresponding to a relevance of the second user interface objectdetermined based on the relevance algorithm and different from the firstdisplayed size of the first user interface object; detecting updatedinput for use by the relevance algorithm; and after detecting theupdated input for use by the relevance algorithm, displaying the seconduser interface object based on the updated input for use by therelevance algorithm, including: in accordance with a determination thatthe relevance of a third user interface object determined based on therelevance algorithm is greater than the relevance of the second userinterface object, displaying the second user interface object having athird displayed size that is smaller than the second displayed size. 13.A non-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display, a movement sensor configured to detectmovement of the electronic device, and a rotatable input mechanismconfigured to rotate with respect to a housing of the electronic device,the one or more programs including instructions for: detecting an inputfrom the movement sensor based on a movement of the electronic device;in response to detecting the input from the movement sensor, displaying,on the display, a first plurality of user interface objects based on arelevance algorithm, wherein the first plurality of user interfaceobjects is selected from a larger plurality of user interface objectsavailable for display, and wherein the first plurality of user interfaceobjects includes a first user interface object associated with a firstapplication and having a first displayed size corresponding to arelevance of the first user interface object determined based on therelevance algorithm; while displaying the first plurality of userinterface objects, receiving a user input, the user input representingrotation of the rotatable input mechanism that rotates with respect to ahousing of the electronic device; in response to receiving the userinput, displaying, on the display, a second plurality of user interfaceobjects based on the relevance algorithm, wherein the second pluralityof user interface objects is selected from the larger plurality of userinterface objects available for display, and wherein the secondplurality of user interface objects includes a second user interfaceobject associated with a second application that is different than thefirst application and having a second displayed size corresponding to arelevance of the second user interface object determined based on therelevance algorithm and different from the first displayed size of thefirst user interface object; detecting updated input for use by therelevance algorithm; and after detecting the updated input for use bythe relevance algorithm, displaying the second user interface objectbased on the updated input for use by the relevance algorithm,including: in accordance with a determination that the relevance of athird user interface object determined based on the relevance algorithmis greater than the relevance of the second user interface object,displaying the second user interface object having a third displayedsize that is smaller than the second displayed size.
 14. The device ofclaim 1, wherein the relevance of the second user interface object isless than the relevance of the first user interface object, and thesecond displayed size of the second user interface object is smallerthan the first displayed size of the first user interface object. 15.The method of claim 12, wherein the first user interface object includesdata corresponding to the first application associated with the firstuser interface object and the second user interface object includes datacorresponding to the second application associated with the second userinterface object.
 16. The method of claim 12, wherein the first userinterface object includes an affordance that causes an action associatedwith the first application to be taken when selected.
 17. The method ofclaim 12, wherein the second user interface object includes anaffordance that causes an action associated with the second applicationto be taken when selected.
 18. The method of claim 15, wherein the datacorresponding to the first application associated with the first userinterface object comprises a notification.
 19. The method of claim 15,wherein the data corresponding to the second application associated withthe second user interface object comprises a notification.
 20. Themethod of claim 12, wherein the relevance algorithm uses as input atleast one of a location of the electronic device, a location of anexternal device, a current time, an upcoming calendar event, mapinformation, or user health information represented by input receivedfrom a biometric sensor.
 21. The method of claim 12, further comprising:displaying a third user interface object and a fourth user interfaceobject, wherein the second user interface object, the third userinterface object, and the fourth user interface object are selectedusing the relevance algorithm, and wherein: the second user interfaceobject includes data associated with the second application, the thirduser interface object includes a notification associated with a thirdapplication, and the fourth user interface object includes an indicationof an action associated with a fourth application.
 22. The method ofclaim 12, wherein displaying the second plurality of user interfaceobjects on the display based on the relevance algorithm comprisesreplacing the first plurality of user interface objects with the secondplurality of user interface objects on the display.
 23. The method ofclaim 12, wherein the relevance algorithm increases a relevance of thesecond user interface object from the larger plurality of user interfaceobjects available for display when a distance between the device and alocation of an external device associated with the electronic devicedecreases.
 24. The method of claim 12, wherein the first plurality ofuser interface objects further includes a third user interface object,wherein the third user interface object overlaps the first userinterface object on the display.
 25. The method of claim 12, wherein therelevance of the second user interface object is less than the relevanceof the first user interface object, and the second displayed size of thesecond user interface object is smaller than the first displayed size ofthe first user interface object.
 26. The non-transitorycomputer-readable storage medium of claim 13, wherein the first userinterface object includes data corresponding to the first applicationassociated with the first user interface object and the second userinterface object includes data corresponding to the second applicationassociated with the second user interface object.
 27. The non-transitorycomputer-readable storage medium of claim 13, wherein the first userinterface object includes an affordance that causes an action associatedwith the first application to be taken when selected.
 28. Thenon-transitory computer-readable storage medium of claim 13, wherein thesecond user interface object includes an affordance that causes anaction associated with the second application to be taken when selected.29. The non-transitory computer-readable storage medium of claim 26,wherein the data corresponding to the first application associated withthe first user interface object comprises a notification.
 30. Thenon-transitory computer-readable storage medium of claim 26, wherein thedata corresponding to the second application associated with the seconduser interface object comprises a notification.
 31. The non-transitorycomputer-readable storage medium of claim 13, wherein the relevancealgorithm uses as input at least one of a location of the electronicdevice, a location of an external device, a current time, an upcomingcalendar event, map information, or user health information representedby input received from a biometric sensor.
 32. The non-transitorycomputer-readable storage medium of claim 13, the one or more programsfurther including instructions for: displaying a third user interfaceobject and a fourth user interface object, wherein the second userinterface object, the third user interface object, and the fourth userinterface object are selected using the relevance algorithm, andwherein: the second user interface object includes data associated withthe second application, the third user interface object includes anotification associated with a third application, and the fourth userinterface object includes an indication of an action associated with afourth application.
 33. The non-transitory computer-readable storagemedium of claim 13, wherein displaying the second plurality of userinterface objects on the display based on the relevance algorithmcomprises replacing the first plurality of user interface objects withthe second plurality of user interface objects on the display.
 34. Thenon-transitory computer-readable storage medium of claim 13, wherein therelevance algorithm increases a relevance of the second user interfaceobject from the larger plurality of user interface objects available fordisplay when a distance between the device and a location of an externaldevice associated with the electronic device decreases.
 35. Thenon-transitory computer-readable storage medium of claim 13, wherein thefirst plurality of user interface objects further includes a third userinterface object, wherein the third user interface object overlaps thefirst user interface object on the display.
 36. The non-transitorycomputer-readable storage medium of claim 13, wherein the relevance ofthe second user interface object is less than the relevance of the firstuser interface object, and the second displayed size of the second userinterface object is smaller than the first displayed size of the firstuser interface object.